MACcess 1.2 is a remote access system for the Macintosh platform. It consists of a server that is run on a host computer and a client program that is used to connect to the host. Also included in the MACcess package is a utility to edit the server settings.
MACcess has a variety of uses and features. It is intended to be used as a method for the owner of a computer to allow people to access certain areas of their hard drive. This is basically Macintosh file-sharing over a TCP/IP connection. Another intended use is for the owner of a computer to be able to get back into their computer from a remote location to do routine maintenance and to get files needed at the time.
MACcess has many useful features that can aid in its intended use. It can browse the directory structure of a remote computer, delete, launch, and rename files, and download any file type of any size. Files are converted and saved in a special format that allows for the quick transfer of Macintosh resource structures. The MACcess client has the ability to both create and transform these special files.
Setup:
Server:
You have two choices of how to run the server application.
1) Put an alias of the server application in your computer's startup folder. This method will cause the server to be running all the time your computer is running. This is the best method if you want people to be able to get in at any time.
2) Run the server application when you know someone is going to need to get into your computer with MACcess. This method will work, as long as you know beforehand when you will need remote access enabled.
Once you have decided how the server will be run, you need to configure it. There are different ways to do this as well. The best method is to use the MACcess Server Setup program that is included with this application. This program will let you edit the server password and create area restrictions. You may also change the password in the server control box.
Server Setup Recap:
1) Decide how you are going to run the server (startup item or on demand.)
2) Configure server with MACcess Server Setup.
SET A PASSWORD! If you don't set a password, anyone could get into your computer! THIS IS THE MOST IMPORTAINT PART OF THIS READ ME! Set a password.
Security Issues:
The nature of MACcess as a remote access system makes it an ovious security issue. I have taken every precaution when writing MACcess in order to protect your security. Like wearing a seatbelt when riding in a car, the best method for protecting your computer is SETTING A PASSWORD. MACcess passwords are stored on your computer and are verified when a person connects. The password is never sent to the remote system, so there is no way to 'hack' or steal the password from the client. The second thing you should do is set up security restrictions. Don't let MACcess access folders that have very importaint files in them. You should know that MACcess will NEVER allow access to the system folder due to security reasons.
The window that pops up when MACcess Server is first run is importaint. It is meant to let the host person know he or she is running the server, so that it can never be secretly installed on an unsuspecting host.
One final note about MACcess security. MACcess has a 'Launch' option. This lets the client run a program on the host's computer. Here again is another reason to have a password. The client can run any program or Apple Script on the host's computer. If you didn't have a password, someone might be able to set up an Apple Script to give them access to the system folder, etc. This is just a note. Remember to set a password.
If you find a security problem, please contact me at cantino@frognet.net. Thank-you.
Testing:
To test the MACcess setup, try running the server, then connecting to yourself with your own IP address.
Known Bugs:
On some computers, attempting to open the trash folder with the client will resault in the server quitting. This quit should not crash the computer, but the server will stop functioning.
Problems:
As with any computer program, it is impossible to say there are no bugs left. If you find any bugs, please e-mail me, describing the bug and the exact situation when it occurred. I can be reached at cantino@frognet.net.
